Autogenerated HTML docs for v2.2.0-rc0 
diff --git a/git-bundle.html b/git-bundle.html index f56426f..83c6dac 100644 --- a/git-bundle.html +++ b/git-bundle.html 
@@ -3,7 +3,7 @@  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">   <head>   <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />  -<meta name="generator" content="AsciiDoc 8.6.6" />  +<meta name="generator" content="AsciiDoc 8.6.9" />   <title>git-bundle(1)</title>   <style type="text/css">   /* Shared CSS for AsciiDoc xhtml11 and html5 backends */  @@ -87,10 +87,16 @@  ul > li { color: #aaa; }   ul > li > * { color: black; }    -pre {  +.monospaced, code, pre {  + font-family: "Courier New", Courier, monospace;  + font-size: inherit;  + color: navy;   padding: 0;   margin: 0;   }  +pre {  + white-space: pre-wrap;  +}     #author {   color: #527bbd;  @@ -219,7 +225,7 @@  }     div.imageblock div.content { padding-left: 0; }  -span.image img { border-style: none; }  +span.image img { border-style: none; vertical-align: text-bottom; }   a.image:visited { color: white; }     dl {  @@ -349,7 +355,7 @@  margin-bottom: 0.1em;   }    -div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {  +div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {   margin-top: 0;   margin-bottom: 0;   }  @@ -407,18 +413,14 @@  span.overline { text-decoration: overline; }   span.line-through { text-decoration: line-through; }    +div.unbreakable { page-break-inside: avoid; }  +     /*   * xhtml11 specific   *   * */    -tt {  - font-family: monospace;  - font-size: inherit;  - color: navy;  -}  -   div.tableblock {   margin-top: 1.0em;   margin-bottom: 1.5em;  @@ -452,12 +454,6 @@  *   * */    -.monospaced {  - font-family: monospace;  - font-size: inherit;  - color: navy;  -}  -   table.tableblock {   margin-top: 1.0em;   margin-bottom: 1.5em;  @@ -537,6 +533,8 @@  @media print {   body.manpage div#toc { display: none; }   }  +  +   </style>   <script type="text/javascript">   /*<![CDATA[*/  @@ -581,7 +579,7 @@    function tocEntries(el, toclevels) {   var result = new Array;  - var re = new RegExp('[hH]([2-'+(toclevels+1)+'])');  + var re = new RegExp('[hH]([1-'+(toclevels+1)+'])');   // Function that scans the DOM tree for header elements (the DOM2   // nodeIterator API would be a better technique but not supported by all   // browsers).  @@ -610,7 +608,7 @@  var i;   for (i = 0; i < toc.childNodes.length; i++) {   var entry = toc.childNodes[i];  - if (entry.nodeName == 'div'  + if (entry.nodeName.toLowerCase() == 'div'   && entry.getAttribute("class")   && entry.getAttribute("class").match(/^toclevel/))   tocEntriesToRemove.push(entry);  @@ -656,7 +654,7 @@  var entriesToRemove = [];   for (i = 0; i < noteholder.childNodes.length; i++) {   var entry = noteholder.childNodes[i];  - if (entry.nodeName == 'div' && entry.getAttribute("class") == "footnote")  + if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")   entriesToRemove.push(entry);   }   for (i = 0; i < entriesToRemove.length; i++) {  @@ -831,7 +829,7 @@  A list of arguments, acceptable to <em>git rev-parse</em> and   <em>git rev-list</em> (and containing a named ref, see SPECIFYING REFERENCES   below), that specifies the specific objects and references  - to transport. For example, <tt>master~10..master</tt> causes the  + to transport. For example, <code>master~10..master</code> causes the   current master reference to be packaged along with all objects   added since its 10th ancestor commit. There is no explicit   limit to the number of references and objects that may be  @@ -858,12 +856,12 @@  <div class="sectionbody">   <div class="paragraph"><p><em>git bundle</em> will only package references that are shown by   <em>git show-ref</em>: this includes heads, tags, and remote heads. References  -such as <tt>master~1</tt> cannot be packaged, but are perfectly suitable for  +such as <code>master~1</code> cannot be packaged, but are perfectly suitable for   defining the basis. More than one reference may be packaged, and more   than one basis can be specified. The objects packaged are those not   contained in the union of the given bases. Each basis can be  -specified explicitly (e.g. <tt>^master~10</tt>), or implicitly (e.g.  -<tt>master~10..master</tt>, <tt>--since=10.days.ago master</tt>).</p></div>  +specified explicitly (e.g. <code>^master~10</code>), or implicitly (e.g.  +<code>master~10..master</code>, <code>--since=10.days.ago master</code>).</p></div>   <div class="paragraph"><p>It is very important that the basis used be held by the destination.   It is okay to err on the side of caution, causing the bundle file   to contain objects already in the destination, as these are ignored  @@ -884,25 +882,25 @@  with an incremental bundle:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>machineA$ cd R1  +<pre><code>machineA$ cd R1   machineA$ git bundle create file.bundle master  -machineA$ git tag -f lastR2bundle master</tt></pre>  +machineA$ git tag -f lastR2bundle master</code></pre>   </div></div>   <div class="paragraph"><p>Then you transfer file.bundle to the target machine B. Because this   bundle does not require any existing object to be extracted, you can   create a new repository on machine B by cloning from it:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>machineB$ git clone -b master /home/me/tmp/file.bundle R2</tt></pre>  +<pre><code>machineB$ git clone -b master /home/me/tmp/file.bundle R2</code></pre>   </div></div>   <div class="paragraph"><p>This will define a remote called "origin" in the resulting repository that   lets you fetch and pull from the bundle. The $GIT_DIR/config file in R2 will   have an entry like this:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>[remote "origin"]  +<pre><code>[remote "origin"]   url = /home/me/tmp/file.bundle  - fetch = refs/heads/*:refs/remotes/origin/*</tt></pre>  + fetch = refs/heads/*:refs/remotes/origin/*</code></pre>   </div></div>   <div class="paragraph"><p>To update the resulting mine.git repository, you can fetch or pull after   replacing the bundle stored at /home/me/tmp/file.bundle with incremental  @@ -911,16 +909,16 @@  incremental bundle to update the other repository:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>machineA$ cd R1  +<pre><code>machineA$ cd R1   machineA$ git bundle create file.bundle lastR2bundle..master  -machineA$ git tag -f lastR2bundle master</tt></pre>  +machineA$ git tag -f lastR2bundle master</code></pre>   </div></div>   <div class="paragraph"><p>You then transfer the bundle to the other machine to replace   /home/me/tmp/file.bundle, and pull from it.</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>machineB$ cd R2  -machineB$ git pull</tt></pre>  +<pre><code>machineB$ cd R2  +machineB$ git pull</code></pre>   </div></div>   <div class="paragraph"><p>If you know up to what commit the intended recipient repository should   have the necessary objects, you can use that knowledge to specify the  @@ -931,23 +929,23 @@  <div class="paragraph"><p>You can use a tag that is present in both:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>$ git bundle create mybundle v1.0.0..master</tt></pre>  +<pre><code>$ git bundle create mybundle v1.0.0..master</code></pre>   </div></div>   <div class="paragraph"><p>You can use a basis based on time:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>$ git bundle create mybundle --since=10.days master</tt></pre>  +<pre><code>$ git bundle create mybundle --since=10.days master</code></pre>   </div></div>   <div class="paragraph"><p>You can use the number of commits:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>$ git bundle create mybundle -10 master</tt></pre>  +<pre><code>$ git bundle create mybundle -10 master</code></pre>   </div></div>  -<div class="paragraph"><p>You can run <tt>git-bundle verify</tt> to see if you can extract from a bundle  +<div class="paragraph"><p>You can run <code>git-bundle verify</code> to see if you can extract from a bundle   that was created with a basis:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>$ git bundle verify mybundle</tt></pre>  +<pre><code>$ git bundle verify mybundle</code></pre>   </div></div>   <div class="paragraph"><p>This will list what commits you must have in order to extract from the   bundle and will error out if you do not have them.</p></div>  @@ -956,12 +954,12 @@  references when fetching:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>$ git fetch mybundle master:localRef</tt></pre>  +<pre><code>$ git fetch mybundle master:localRef</code></pre>   </div></div>   <div class="paragraph"><p>You can also see what references it offers:</p></div>   <div class="listingblock">   <div class="content">  -<pre><tt>$ git ls-remote mybundle</tt></pre>  +<pre><code>$ git ls-remote mybundle</code></pre>   </div></div>   </div>   </div>